Mobile emergency response network

ABSTRACT

A mobile emergency response network may be utilized to respond to emergencies. Emergency response resources may be selected and deployed through the use of network communications between user equipment and network elements. In an example configuration, a mobile emergency response network may receive emergency data, determine an emergency is occurring, determine a resource requirement for the emergency, identify a mobile device associated with a user who meets the resource requirement, and send a request to the mobile device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/180,602, filed on Jun. 13, 2016, which is incorporated herein byreference in its entirety.

BACKGROUND

Emergency response services are coordinated by a series of isolated,discrete systems typically organized at a tier of local government, suchas at the county level in the United States. These systems, referred togenerally in the United States as public safety answering points (PSAP),are unable to coordinate targeting of emergency responders andemergencies due to the technological limitations of existing systems.Furthermore, while certain fire, police, or ambulatory services may beavailable to assist with an emergency, those resources may be leveragedinefficiently or not at all due to the network limitations of PSAPs.

SUMMARY

As disclosed herein, a mobile emergency response network may provide acontrol framework for detecting emergencies and managing and directingemergency response resources. Interactive controls may be generated forcommunications between multiple devices across heterogeneouscommunication networks within the emergency response network.

In an aspect, an emergency services server for a mobile emergencyresponse network may include a processor and memory coupled to theprocessor. The memory may include executable instructions that whenexecuted by the processor cause the processor to effectuate operations.The operations may include receiving, from a first remote mobile deviceover a first wireless communication channel, a first emergency messageincluding a first multimedia data file. The first multimedia data filemay include first metadata. The operations may also include receiving,from a second remote mobile device over a second wireless communicationchannel, a second emergency message including a second multimedia datafile. The second multimedia data file may include second metadata. Theoperations may also include separating the first multimedia data filefrom the first emergency message, extracting a first location value fromthe first metadata, separating the second multimedia data file from thesecond emergency message, and extracting a second location value fromthe second metadata. The operations may also include aggregating thefirst multimedia data file and the second multimedia data file,generating an emergency responder request including the aggregated firstand second multimedia data files, and defining, based on the firstlocation value and the second location value, a candidate region. Theoperations may also include identifying a candidate mobile device withinthe candidate region, wherein the candidate mobile device is not thefirst remote mobile device or the second remote mobile device, andtransmitting the emergency responder request over a third wirelesscommunication channel to the candidate mobile device.

In an aspect, a method for implementing a mobile emergency responsenetwork may include an emergency services server receiving from a firstremote mobile device a first emergency message including a firstmultimedia data over a first wireless communication channel. The firstmultimedia data may include first metadata. The method may also includethe emergency services server receiving from a second remote mobiledevice over a second wireless communication channel a second emergencymessage including a second multimedia data file. The second multimediadata file may include second metadata. The method may also include theemergency services server separating the first multimedia data file fromthe first emergency message. The method may also include the emergencyservices server extracting a first location value from the firstmetadata. The method may also include the emergency services serverseparating the second multimedia data file from the second emergencymessage. The method may also include the emergency services serverextracting a second location value from the second metadata. The methodmay also include the emergency services server aggregating the firstmultimedia data file and the second multimedia data file. The method mayalso include the emergency services server generating an emergencyresponder request including the aggregated first and second multimediadata files. The method may also include the emergency services serverdefining, based on the first location value and the second locationvalue, a candidate region. The method may also include the emergencyservices server identifying a candidate mobile device within thecandidate region, wherein the candidate mobile device is not the firstremote mobile device or the second remote mobile device. The method mayalso include the emergency services server transmitting the emergencyresponder request over a third wireless communication channel to thecandidate mobile device.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to implementations that solveany or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described mobile emergency response network aredescribed more fully herein with reference to the accompanying drawings,in which example embodiments are shown. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide an understanding of the various embodiments. However,the instant disclosure may be embodied in many different forms andshould not be construed as limited to the example embodiments set forthherein. Like numbers refer to like elements throughout.

FIG. 1 is a depiction of an exemplary network environment in which oneor more disclosed examples may be implemented for a mobile emergencyresponse network.

FIG. 2 is a depiction of an example emergency setting illustratingaspects of the present disclosure.

FIG. 3 is a depiction of a device illustrating aspects of the presentdisclosure.

FIG. 4 is a depiction of an exemplary flow chart illustrating aspects ofthe present disclosure.

FIG. 5 is an exemplary diagram illustrating aspects of the presentdisclosure.

FIG. 6 is a depiction of an exemplary flow chart illustrating aspects ofthe present disclosure.

FIG. 7 is a depiction of an exemplary dashboard illustrating aspects ofthe present disclosure.

FIG. 8 is a block diagram of an exemplary mobile emergency network.

FIG. 9 is a block diagram of an example mobile device which may beutilized to facilitate mobile emergency response network.

FIG. 10 is a block diagram of an exemplary processor in which one ormore disclosed examples may be implemented for a mobile emergencyresponse network.

FIG. 11 is a block diagram of an exemplary packet-based mobile cellularnetwork environment, such as a GPRS network, in which one or moredisclosed examples may be implemented for a mobile emergency responsenetwork.

FIG. 12 illustrates a non-limiting exemplary architecture of a typicalGPRS network, segmented into four groups, in which one or more disclosedexamples may be implemented for a mobile emergency response network.

FIG. 13 illustrates a non-limiting alternate block diagram of anexemplary GSM/GPRS/IP multimedia network architecture in which one ormore disclosed examples may be implemented for a mobile emergencyresponse network.

FIG. 14 illustrates a Public Land Mobile Network (PLMN) block diagramview of an exemplary architecture in which one or more disclosedexamples may be implemented for a mobile emergency response network.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1 illustrates an example telecommunication system for a mobileemergency response network. As shown in FIG. 1, user equipment 100 mayrequest a service, execute an application, perform an operation, or thelike, from entity 140, via radio access technology 120 and a simplifiedtelecommunications network 136. Telecommunications network 136 mayinclude an emergency services server 138. As depicted in FIG. 1, userequipment 100 may comprise any appropriate type of user equipment, suchas, for example, smartphone 104, tablet 108, camera 112, detector 116(such as, for example, a smoke and/or carbon monoxide detector), atelematics unit (not shown), or the like, or any appropriate combinationthereof. It is to be understood that user equipment 100 as depicted inFIG. 1 is exemplary and not intended to be limiting. User equipment maygain access to network via any appropriate mechanism. For example, asdepicted in FIG. 1, access to network may be provided via cellularinfrastructure, Wi-Fi™ infrastructure, hot spots, or the like, or anyappropriate combination thereof. FIG. 1 depicts, as examples, macro cell124 (e.g., LTE, 5G, etc.), Wi-Fi™ access point 128, and micro or metrocell 132. It is to be understood that radio access technology 120 asdepicted in FIG. 1 is exemplary and not intended to be limiting.

FIG. 2 is an overhead view of a depiction of emergency 200 illustratingaspects of the present disclosure. Scenario 200 may take place instructure 204 as a result of an emergency event 202. Event 202 may be aninstant occurrence or multiple occurrences of the same type or differenttypes. For example, event 202 may be a gas leak at time t₀, but at timet₁, may include one or more explosions, and at time t₂, may include oneor more fires. As another example, event 202 may be a robbery at t₀, butmay escalate to, for example, an assault at t₁, and there may be amedical emergency for victims following the shooting or assault. Event202 is not limited to a static emergency and may include a dynamicscenario. Event 202 is shown as taking place within structure 204 forillustrative purposes only and is not limited to occurrences withinbuildings or enclosed environments—event 202 may be partially or totallywithin one or more structures, partially or totally outside of anystructure, and may occur over time to encompass multiple environs. Forexample, at t₀, event 202 may be entirely within structure 204, but att₁, event 202 may encompass areas outside of structure 204. As anexample, event 202 may be a fire contained within structure 204 at t₀,but may spread beyond structure 204 at t₁. As another example, event 202may begin at t₀, and a different, distinct event may occur at t₁ (orvice-versa, such that event 202 occurs after a preexisting event). Event202 may initially overlap or not overlap with the other event, and maylater overlap with the other event at, for example, t₂. For example,event 202 may comprise seismic activity, such as an earthquake, in afirst area, such as structure 204, and the other event may compriseseismic activity in a second area. Event 202 may be a subset of a largerscale event and may arise from other events. For example, event 202 maybe a person trapped beneath rubble after structure 204 has a structuralfailure. The failure may occur, for example, independently of events,but may also be precipitated or directly caused by another event, suchas, for example, a vehicle collision (with structure 204), seismicactivity, flooding, or ground movement, such as a landslide or sinkhole.

Structure 204 may have one or more detectors 116, such as detector 216and detector 220. Detectors 216 and 220 may form or be part a networkindividually or together. For example, detectors 216 and 220 mayindividually or both be connected to a LAN (or different LANs) which maybe shared with over devices such as camera 208. For example, detector216 may connect to a LAN shared with camera 208 while detector 220 mayconnect to an LTE or 5G network through picocell 224. Detectors 216 and220 may connect to the LAN via a wired or wireless connection, such asthrough wireless access point 212 or 213. Detectors 216 and 220 mayalso, independently or in response to a signal, connect with otherdevices, such as camera 208 or smartphones 104 associated with, forexample, user 240 or 244. Detectors 216 and 220 may connect directlywith other devices, such as camera 208 or smartphones 104 through, forexample, wired connections or wireless connections such as Bluetooth™ orinfrared (IrDA). Detectors 216 and 220 may be mounted on walls,including ceilings, or within systems such as, for example, heating,ventilating, and air conditioning (HVAC) systems. For example, detectors216 and 220 may be within ducts or connected with ducts, such as a ductconnected with vent 228, fluidly or communicatively (e.g., connection toduct control system or sensors). Detectors 216 and 220 may be part of orconnected with a fire protection system, such as, for example, a wateror foam water sprinkler system. For example, detectors 216 and 220 mayinclude a temperature sensor and may indicate for or cause water to bereleased through sprinkler heads when the ambient temperature exceeds athreshold. As another example, detectors 216 and 220 may include ahumidity sensor, which may, for example, determine air moisture levelsto indicate for or cause water flow through sprinkler heads to start,increase, decrease, or stop. As yet another example, detectors 216 and220 may include a vibration sensor or seismometer and may indicate, forexample, motions of structure 204 or ground motion. For example,detectors 216 and 220 may indicate stresses on a structural component ofstructure 204. Detectors 216 and 220 may indicate when, for example,stress exceeds a threshold. This may be, for example, vibration in aload-bearing column of structure 204. As another example, detectors 216and 220 may include or be included in, for example, a seismic damper. Asyet another example, detectors 216 and 220 may include an audio sensoror audio capture device, such as a microphone. Detectors 216 and 220 maygenerate an acoustic profile of audio captured or otherwise received bydetectors 216 and 220. The acoustic profile may be used, for example, bydetector 216 and 220 to determine a gunshot has been fired and thelocation of the gunshot.

Structure 204 may have one or more cameras, such as cameras 208 and 248.Camera 248 may, for example, be configured to overlook exterior featuresof structure 204 and environmental assets or features and transportationor navigational asserts or features of the area around structure 204.For example, camera 248 may encompass in its field of visionthoroughfare 264. Thoroughfare 264 may include, for example, one or moreof a road, sidewalk, trail, or a parking lot. Structure 204 and the areasurrounding structure 204 may have specialized resources for emergencysituations. For example, emergency resource 260 may be a hydrant, suchas, for example, a freestanding or non-freestanding hydrant, which maybe pressurized or non-pressurized.

Structure 204 may have multiple ingress-egress points, such asingress-egress points 232 and 236. Ingress-egress points 232 and 236 mayinclude, for example, one or more doors or windows. Ingress-egress point236 may be, for example, an emergency exit. Ingress-egress point 236 mayinclude, for example, a sensor, such as a motion sensor, connected withone or more alarms, such as alarm 218 or 219. Ingress-egress points 232and 236 may have electronic controls and electronic locks, which may beconnected with one or more security systems of structure 204.

Cameras 208 and 248 may comprise user equipment 100, and may comprisecamera 112. Cameras 208 and 248 may include one or more sensors, suchas, for example, a motion detector. Cameras 208 and 248 may have audiocapturing devices such as microphones. Cameras 208 and 248 may beconnected, wirelessly or wired, with one or more networks. For example,cameras 208 and 248 may be connected with a local area network (LAN) viaa wired connection or wirelessly through, for example, wireless accesspoint 212 or 213. Alternatively or additionally, cameras 208 and 248 maybe connected with another network, for example, an LTE or 5G networkdirectly or through, for example, picocell 224. Cameras 208 and 248 mayconnect to one or more networks selectively. Using the instant example,camera 208 may have a constant, substantially constant, or intermittentconnection to a LAN through, for example a wired or wireless connection.Cameras 208 and 248 may also be capable of making a connection to theLTE or 5G network, but only does so based on an event trigger orrequest. For example, camera 208 or 248 may operate to send images (suchas streaming video or sending still images) over the LAN connection inresponse to a wake-up signal responsive to a sensor of camera 208 or248, such as a motion detector, or a separate sensor or device, such asdetector 216 or 220 or alarm 218 or 219. Cameras 208 and 248 may alsocontrol functions of alarm 218 or 219, such as alert functions. An alertmay include one or more audible alerts (e.g., siren or warningbroadcast) or visual alerts (e.g., strobe lights). Cameras 208 and 248may connect to an LTE or 5G network through, for example, macro cell 252or an intermediate device that can share such a connection, such aspicocell 224 or a hotspot (using, for example, a Wi-Fi™ connection) inresponse to, for example, a signal from the LTE or 5G network, a signalfrom a LAN, or a signal from smartphone 104. Smartphone 104 may beassociated with, for example, user 240 or 244, or a user not withinstructure 204, such as user 256, who may be an emergency responder.Smartphone 104 may also be associated with multiple users, such as, forexample, an emergency responder group or unit). One or more users may beassociated with one or more smartphones 104 (or other user equipment100) by, for example, a Subscriber Identity Module (SIM) or a UniversalIntegrated Circuit Card (UICC) of the smartphone, which may include anInternational Mobile Subscriber Identity (IMSI). An IMSI may be used by,for example, a Home Location Register (HLR) or Visitor Location Register(VLR).

One or more of cameras 208 and 248, detectors 216 and 220, alarms 218and 219, ingress/egress points 232 and 236, access points 212 and 213,and picocell 224 may be part of a security system network. Structure 204may have a security system associated with it. This security system mayinclude a controller in communication with other devices, such ascameras 208 and 248, detectors 216 and 220, alarms 218 and 219,ingress/egress points 232 and 236, access points 212 and 213, andpicocell 224. The controller may be in communication with an externalserver, such as, for example, a monitoring center server. The controllermay send “arm/disarm” commands to devices it is in communication with.An “arm” command may enable a device. Enablement may occur according toone or more of a schedule, on a trigger, or immediately. Similarly, a“disarm” command may disable a device. This may occur according to oneor more of a schedule, on a trigger, or immediately.

Smartphone 104 may be in communication with one or more of cameras 208and 248, detectors 216 and 220, alarms 218 and 219, and ingress/egresspoints 232 and 236. For example, smartphone 104 may connect with a LANthrough a wireless connection using, for example, access point 212 or213. Smartphone 104 may also be connected to a cellular network, such asan LTE or 5G network, through, for example, picocell 224 or macro cell252. Smartphone 104 may poll devices. Polling may be done, for example,to determine if there is information available or if the device isavailable. Smartphone 104 may automatically poll devices or may, forexample, poll in response to a request. User 240 may, for example, maygenerate a request to poll available devices using smartphone 104.Smartphone 104 may then poll for available devices and generate a reportbased on the responses or lack of responses to the polling. For example,smartphone 104 may generate a report including the available devices andinformation regarding the available devices, such as the type of deviceand its capabilities. Unavailable or unresponsive devices may also beincluded. For example, smartphone 104 may have polled at an earlierpoint in time when camera 208 indicated it was available. However,camera 208 may at the current time indicate it is unavailable. Thereport may indicate the unavailability of camera 208. Smartphone 104 maydisplay the report. The report may be interactive. For example, user 240may select an available device on smartphone 104 to generate a requestto retrieve data from that available device.

Independent of or in conjunction with the use of polling or pollingreport generation, smartphone 104 may generate requests and send therequests to devices such as, for example, detectors 216 and 220, alarms218 and 219, and ingress/egress points 232 and 236. A request may besent to a server in communication with the device. For example, camera208 may be in communication with a media server. A request may be sentto the media server for information from camera 208 or another device.

Smartphone 104 may also receive information sent from devices. Forexample, detector 216 may broadcast an indication that carbon monoxidelevels are high. Smartphone 104 may receive this indication and may, forexample, render it on the display. The broadcast may be in the form of apush notification, for example. As another example, smartphone 104 mayreceive the broadcast from a server which is in communication withdetector 216. Smartphone 104 may render this information and display itusing display 304.

FIG. 3 is a depiction of smartphone 104 illustrating aspects of thepresent disclosure. Smartphone 104, as depicted in FIG. 3, may includedisplay 304. A user interface of an application is depicted as beingdisplayed on display 304. The application may be client software. Theuser interface includes attachment fields 308, 312, 316, and 320, textinput field 324, and command button 328. A user may generate, using theuser interface of the application, an emergency request. The emergencyrequest may include a description of the emergency entered in text inputfield 324. The emergency request may also include data, such asmultimedia data. For example, a user may select a video file forinclusion, such as the video file listed in attachment field 320, anaudio file, such as the audio file listed in attachment field 316, or animage file, such as the image file listed in attachment field 312. Theuser interface may continue to provide additional attachment fields,such as attachment field 308, as the user continues to attach additionalfiles. One or more limits may be imposed, such as a request size limit.The limits may be imposed by the application as either set directly bythe application on smartphone 104, such as through a user preference.The limits may also be set by a third party, such as emergency servicesserver 138, and then enforced by the application on smartphone 104. Forexample, a 1 megabyte size limit may be set. Smartphone 104 may transmitan emergency request to emergency services server 138. Command button328 may be used to execute send/transmit commands or other commands.Additional information may be appended to files. For example, a user mayadd geographic location data to a file. For example, when a user selectsa file to be included with the request, the user may, with or withoutprompting, select geographic coordinates to append to the file. Forexample, a user may not be in the same geographic location as theemergency. The user may receive an image file taken of the emergency.The image may originate from the location of emergency 200. For example,it may have been generated using a camera (or device equipped with acamera) and transmitted to smartphone 104. The user may tag the filewith location data. The location data may then be used by emergencyservices server 138 as at least part of a determination of the locationof the emergency.

Smartphone 104 may receive a communication from emergency server 138.For example, emergency services server 138 may have received anemergency request originating from either smartphone 104 or anotherdevice. In response, emergency server 138 may send a message tosmartphone 104. Text included in the message may be rendered in textinput field 324. This may be displayed as, for example, a dialog.Communication between smartphone 104 and emergency server 138 may beaccording to, for example, the Extensible Messaging and PresenceProtocol (XMPP). Emergency services server 138 may, accordingly, supportXMPP or be an XMPP server. Communications may also include additionalparties, such as in the case of multi-user chat. For example, multipleusers may connect to emergency services server 138 and be connected in amulti-user chat. Users may be connected in a multi-user (or one-on-onechat) based at least in part on, for example, emergency requestssubmitted by each of the respective users or a subset of the users. Forexample, a user may submit an emergency request to emergency servicesserver 138 using smartphone 104. Emergency services server 138 mayconnect smartphone 104 into a chat with a device associated with anemergency responder.

FIG. 4 is a depiction of an exemplary flow chart illustrating aspects ofthe present disclosure. At 400, emergency data is received by emergencyservice server 138. Emergency data may include, for example, one or moreof an audio recording, an SMS or MMS message, an email, a video, animage, an alert. The emergency data may be transmitted from userequipment 100. For example, the emergency data may be an emergencyrequest received from smartphone 104. For example, in reference to FIG.2, user 244 may be associated with smartphone 104. Smartphone 104 mayinclude an application which may package video, images, text, audio, andother data into an emergency request as depicted in FIG. 3. This datamay be generated by smartphone 104 or other devices. For example,smartphone 104 may include a camera and it may be used to generate avideo file. Smartphone 104 may also include data from other sources. Forexample, smartphone 104 may receive a video from tablet 108 associatedwith user 240. Smartphone 104 and tablet 108 may both be connected to aLAN using wireless access points 212 or 213. The emergency request mayalso include attributes based on analysis of the data included with therequest.

Emergency data may also include an indication of an emergency from aPSAP. Emergency response server 138 may also be associated with one ormore PSAPs and may receive the indication from another PSAP thatemergency response server 138 is associated with or not. For example, aPSAP may receive a 911 call. On reception, the PSAP may transmit to theemergency service server 138 a message indicating the emergency. Inanother example, emergency response server 138 may be a PSAP server. Asanother example, emergency response server 138 may provide a dashboardor a website. As an example, emergency response server 138 may generatea dashboard on a PSAP client device. The client-side dashboard may be auser interface the PSAP (or other client-side entity or user) may use tosend commands and information to emergency response server 138 andreceive and render information from emergency response server 138. Thismay allow, for example, the customization of views or presented dataaccording to use preference.

FIG. 4 is a depiction of an exemplary flow chart illustrating aspects ofthe present disclosure. At 400, emergency services server 138 receivesemergency data. Emergency data may be, for example, one or moreemergency requests or included in an emergency request. For example, anemergency request may be generated using smartphone 104 and received byemergency server 138. As another example, emergency data may include a911 call. Information from the call may be received by emergency server138 such as, for example, from a PSAP operator. As another example,emergency data may include alert data. For example, emergency servicesserver 138 may receive alert data from detector 216. For example,detector 216 may include a motion sensor and may indicate that motionhas been detected. As another example, detector 216 may include a carbonmonoxide sensor and may indicate carbon monoxide levels, such as whenlevels have exceeded a threshold. Emergency services server 138 mayseparate certain elements of an emergency request from the emergencyrequest, or may, for example, isolate certain elements entirely. Forexample, emergency services server 138 may separate, for example,multimedia files, header information, or other information that is, forexample, not text content from an emergency request. Multimedia files,header information, or other information separated from an emergencyrequest may be isolated from any other information separated from theemergency request. This may be done, for example, based on file type.For example, multimedia files may be separated from an emergency requestbut an image file (as opposed to, for example, an audio or video file)may be specifically isolated.

At 402, emergency services server 138 determines whether an emergencyexists and, if so, the scope of the emergency. Emergency server 138 maydetermine whether an emergency exists based on, for example, the receiptof an emergency request. Emergency server 138 may determine whether anemergency exists using, for example, a flag or trigger. For example,emergency server 138 may receive an emergency request from smartphone104 but may not determine if an emergency exists until receivingconfirmation. Emergency server 138 may request confirmation or may havealready received other information indicating an emergency. For example,a PSAP operator may receive a 911 call with details of an emergency. ThePSAP operator may then indicate to emergency server 138 that anemergency exists. Emergency server 138 may then determine that anemergency exists. For example, a PSAP operator may indicate to emergencyserver 138 that an emergency exists. The PSAP operator may provideinformation to emergency server 138, such as, for example, a location,an emergency type, a phone number (such as a caller phone number), anidentity (such as a caller's identity in the form of a name, SocialSecurity number, driver's license number, date of birth, or otherpersonally identifiable information), or other information. Emergencyserver 138 may also receive authorization to retrieve personalidentification information and may retrieve that information from one ormore databases, such as, for example, through a request to one or moreservers. Emergency services server 138 may log emergency requests in adatabase including information about the request, including a timestampand one or more attributes.

At 404, emergency services server 138 generates resource requirementsfor a response to the emergency. Resource requirements may includeequipment requirements. For example, one or more firearms (or firearmsof a certain class, such as a pistol or rifle, or model, such as an M4),munitions (such as breaching rounds or flashbangs), one or more vehicles(such as a fire engine or hazardous materials vehicle), one or moretools (such as a ram or a cutter), medical supplies (such as adefibrillator), or sets of equipment (such as a set of scuba gear).Resource requirements may include animal resources, such as one or morecanines (or a subset of canines, such as detection canines). Resourcerequirements may be more detailed. For example, a requirement for avehicle may include a requirement that the vehicle have certainresources, capabilities, or features. For example, a vehicle may berequired to have a locker with certain weaponry, a ladder capable ofextending a certain minimum length, a threshold amount of fuelavailable, or all-wheel drive. Resource requirements may include userequipment 100. For example, resource requirements may include smartphone104, or that smartphone 104 have certain functions or capabilities. Forexample, resource requirements may include a requirement that smartphone104 have specific software or hardware. For example, it may include arequirement that a smartphone have installed a specific application. Itmay further include a requirement that the specific application is in acertain mode or that smartphone 104 is in a specific mode. Resourcerequirements may also include personnel. For example, one or more policeofficers, one or more firefighters, one or more paramedics, or one ormore animal control officers. Personnel resource requirements mayinclude role, position, or rank. For example, non-volunteer,non-trainee, special weapons and tactics team member, aquatic rescueteam member, or sniper. Personnel resource requirements may includespecific skills, certifications, or experience. For example, helicopterpiloting, diving, heavy equipment operation, or language fluency.

At 406, emergency services server 138 generates a candidate region. Acandidate region may be defined by a series of coordinates, which may bedetermined or expressed as Global Positioning System (GPS) coordinates.The coordinates may follow a coordinate system, such as, for example, ageographic coordinate system such as longitude and latitude. A candidateregion may be instructions for defining a candidate region, including aninitial region and then additional regions to be set based on whetherconditions are met. For example, if the resource requirements are notmet using a first candidate region, a second candidate region may bedefined. A candidate region may be, for example, an entire area within astraight-line geographical distance from the emergency. As anotherexample, a candidate region may be based on estimated travel time, wheretravel time may be based on the vehicle or other transportationequipment available and traffic information.

At 410, emergency services server 138 determines the sufficiency of thecandidate set. Sufficiency may be determined by a scoring. For example,personnel resource requirements may correspond to a numerical scorebased on one or more skill requirements, health requirements, orexperience requirements. A candidate personnel resource may have anassigned score if the personnel resource is already within a databaseaccessible to emergency services server 138. Emergency services server138 may also retrieve from smartphone 104 associated with a candidatepersonnel resource information to determine a candidate personnel score.If a personnel resource score of a candidate is insufficient, then arequest may not be sent to user equipment 100 associated with thatcandidate personnel resource, or the request may be, for example, givena lower priority.

At 410, it is determined if all the available resources could possiblymeet the resource requirements of the emergency. For example, multipletypes of resources may be required. For example, three police officers,a fire engine with five firefighters, and an ambulance with twoparamedics may be needed. If, for example, only two police officers arewithin the candidate region, the candidate set is insufficient. If thecandidate set is insufficient, at 412, emergency services server 138generates a new candidate zone. The resources within the insufficientcandidate region may not be requested or may be requested. This may be,for example, an expanded candidate zone corresponding to a greatergeographical area. If the candidate set is sufficient, at 414, emergencyservices server 138 requests a candidate.

FIG. 5 is an overview of a depiction of an exemplary diagramillustrating aspects of the present disclosure. FIG. 5 depicts tworegions: region 501 and region 502, defined by dotted lines. Regions 501and 502 may be defined by a series of coordinates, which may bedetermined or expressed as Global Positioning System (GPS) coordinates.The coordinates may follow a coordinate system, such as, for example, ageographic coordinate system such as longitude and latitude. Region 501and region 502 share border 503. Region 501 and region 502 may defineboundaries of geographical regions based on, for example, administrativeor governmental regions. Regions 501 and 502 may correspond with, forexample, the borders of counties or municipalities. Region 501 andregion 502 may also encompass several geographical regions and types ofregions, such as multiple counties, multiple municipalities, schoolzones, transit systems, overlays, or jurisdictions. Regions 501 and 502may also, for example, be defined in whole or in part by networkinfrastructure. For example, regions 501 and 502 may be defined by oneor more macro cells 124. Regions 501 and 502 may also be defined byhomogeneous or heterogeneous network elements, such as, for example, oneor more macro cells 124, one or more micro cells 132, and one or moreaccess points 128. Regions 501 and 502 may have a dynamic size andborder. Regions 501 and 502 may change in size based on, for example,cellular network traffic, user equipment volume, or user preference.Regions 501 and 502 may be generated or modified by or through, forexample, a dashboard or website, or may be used to generate or modify adashboard or website. Regions 501 and 502 may also be subject toconstraints. For example, an outer bound may be set based on one or morepolitical, jurisdictional, or administrative boundaries. The outer boundmay be a set of coordinates corresponding to one or more of suchpolitical, jurisdictional, or administrative boundaries. Otherconstraints may be to include only areas within the broadcast range ofradio access technology 120. For example, one or more macro cells 124 orsimply “all” macro cells 124, one or more micro cells 132 or simply“all” micro cells 124, one or more access points 128 or simply “all”access points 128, or a combination of one or more of these types ofradio access technology 120. As another example, it may be constrainedto those areas where the radio access technology 120 provides at least athreshold level of Quality of Service (QoS), available bandwidth,network technology (e.g., 3G; LTE, or 5G), or a combination of one ormore of these constraints.

For example, the Federal Emergency Management Agency (FEMA) may declarean area a disaster area. Entity 140 may be or include a server or andmay generate, for example, an Extensible Markup Language (XML) orKeyhole Markup Language (KML) file defining the declared area of theemergency. Alternatively or additionally, entity 140 may generate datawhich may be received from entity 140 or requested from entity 140 andmay be used to, for example, generate or modify one or more XML or KMLfiles. The file may be modified or a new file may be generated from thedata in the file to be used to define regions 501 and 502. The declaredarea of the emergency data received from entity 140 may be used togenerate, for example, an interactive view for a dashboard or website.Regions 501 and 502 may then be further defined by constraints. This mayreduce regions 501 and 502 to those areas where, for example, athreshold level of network bandwidth is available. This may also reduceregions 501 and 502 to the area or areas indicated by a user such as,for example, through an interactive view. The interactive view may bepresented in a user interface such as, for example, through a dashboard.While regions 501 and 502 are depicted, one region or more than tworegions are within the scope of the present disclosure.

The location of emergency 200 is indicated on FIG. 5. As shown in FIG.5, emergency 200 is located within region 501. Emergency 200 may have anemergency zone 528 created or associated with it. Emergency zone 528 isan area encompassing at least the known or estimated immediategeographic scope of emergency 200. Emergency zone 528 may include awider area based on information received regarding the emergency. Forexample, if emergency 200 includes only a car accident, then emergencyzone 528 may have a relatively small fixed size, such as a fixed radiusor diameter, or a fixed distance along a roadway, from the car accident.If emergency 200 includes a shooting, then emergency zone 528 may have agreater size if, for example, the suspected shooter or shooters areunaccounted for or mobile. This may be determined based at least in parton, for example, an emergency request received from smartphone 104. Forexample, an emergency request may include an audio file. The audio filemay be analyzed by emergency services server 138. Based on the analysis,emergency services server 138 may determine that the audio indicates anautomobile wreck has occurred, or indicates a probability that anautomobile wreck has occurred. Based on that indication, emergency zone528 may be set or adjusted. For example, emergency zone 528 may be setas ten meters from the location of the emergency 200. The location ofemergency may be, for example, assumed to be the location of a source ofan emergency request. This assumption, however, may be adjusted,overridden, or replaced based on other information. The location of thesource of the emergency request may be determined by, for example, acell ID of a base station that received the emergency request,multilateration-based timing, or Wi-Fi localization. The location ofemergency 200 (and emergency zone 528) may also be set or adjusted usingdata given in an emergency request. For example, processing of a videosubmitted with an emergency request may determine a landmark within thevideo and, based on that determination, set or adjust the location ofemergency 200. As another example, a user may include a street addressin the emergency request and the street address may be used to set oradjust the location of emergency 200. For example, the user may includethe street address using text input field 324. Similarly, image filesmay be processed to determine landmarks. Metadata may also be analyzedto determine or adjust the location of emergency 200. A video file,audio file, or image file, for example, submitted with the emergencyrequest may include metadata. For example, an image file may includemetadata (such as Exchangeable image file format (Exif) structured data)specifying location (such as GPS data) and time information. Metadatamay be extracted from the files and analyzed, transmitted, aggregated,or stored separately and independently from the files.

Emergency response resources 504, 508, 512, 516, 320, 528, 532, 536, and540 are shown within regions 501 and 502. Emergency response resources504, 508, 512, 516, 320, 528, 532, 536, and 540 may be, for example,military, police, fire, or ambulatory resources. For example, emergencyresponse sources 504, 508, 512, 516, 320, 528, 532, 536, and 540 may bepersonnel or groups of personnel or assets. Personnel may be associatedwith user equipment 100. Assets or equipment may be or include userequipment 100. For example, a police asset may be a vehicle, such as acar, motorcycle, van, truck, riot control vehicle (e.g., armoredpersonnel carrier), or all-terrain vehicle, or aircraft, such as, forexample, a helicopter, blimp, or unmanned aerial vehicle. A police car,for example, may include user equipment 100 such as, for example, atelematics unit. Emergency response resources 504, 508, 512, 516, 320,528, 532, 536, and 540 may include both an asset, such as a fire engine,and personnel, such as one or more firefighters.

FIG. 6 is a depiction of an exemplary flow chart illustrating aspects ofthe present disclosure. At 600, user equipment 100 receives a candidaterequest. For example, smartphone 104 may receive a candidate request.The candidate request may be a push message. Smartphone 104 may beassociated with a particular user, such as, for example, an emergencyresponder. Association may be determined, for example, by authenticationthrough smartphone 104. For example, smartphone 104 may require one ormore of a password, an answer to a challenge question, or a personalidentification number. Emergency server 138 may receive theauthentication. An authentication server may also receive theauthentication and provide the authentication to emergency server 138.Authentication server may be a device management server. Devicemanagement server may provision user equipment 100. Device managementserver may provision user equipment 100 to particular user accounts.User accounts may be associated with particular individuals or groups.Device management server may provide this association to emergencyserver 138. For example, an emergency response organization, such as amunicipal police department, may have a device management server. Devicemanagement server may provision user equipment 100 for specific policeofficer user accounts. For example, smartphone 104 may be provisioned toa police officer user account. The association of smartphone 104 withthe police officer user account may be provided by the device managementserver to emergency server 104. For example, smartphone 104 may beassociated with a police officer user account by, for example,International Mobile Equipment Identity (IMEI), SIM, or UICC. The entireuser account may be provided by the device management server to theemergency services server 138. For example, emergency services server138 may communicate using the Simple Object Access Protocol (SOAP). Adevice, such as a device management server, may connect to emergencyservices server 138. This connection may be, for example, a HypertextTransfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS)connection. Emergency services server 138 may receive a SOAP messagefrom a device management server. The message may include formatted dataproviding user account information, such as an identifier of smartphone104 (such as an IMEI or IMSI), user account status (such as active,inactive, locked, or last login time), phone number, email address,username, password, permissions, or user identity. The message may alsoinclude formatted data providing skills information, such as number ofyears active duty, classification (such as police, ambulatory/paramedic,or firefighter), rank, pay grade, group membership (such as a unit orparticular security detail), or equipment certified for or qualified on(such as certain firearms, vehicles, or tools). The message may alsoinclude certain individual attributes, such as gender or disability, andmeasurements of weight, height, and health or fitness (such as anability to carry a certain load a certain distance within a certainamount of time or complete a one kilometer run within a certain amountof time), or indications of current or past injuries. The message mayalso include formatted data providing availability information, such asa shift schedule or indication of on duty or off duty (such as a flag).Emergency server 104 may use the identification of the police officeruser account to identify skills, certifications, equipment, and otherrecords. For example, emergency server 104 may include a database ofthis information, may receive it from the device management server (suchas with the association information), or may request it from athird-party database. Emergency services server 138 may save thesemessages in a database, and may use the information contained in themessages to create or update entries in a database. Emergency servicesserver 138 may be or act as an authentication server or devicemanagement server. Emergency services server 138 may be virtualized inwhole or in part. For example, emergency services server 138 (or one ormore of its functions) may be a virtualized application or virtualmachine run on a computing device such as a server.

If there is a denial, at 604, a denial response may be sent usingsmartphone 104. The denial response may include, for example, a messageexplaining the denial. The denial response may be automatic. Forexample, it may be indicated on smartphone 104 that the user is engagedalready. The engagement may be indicated to be a priority level, such asa low, medium, or high priority level. The engagement may be indicatedusing a classification code. Indication of the engagement may be used todisable prompts and automatically respond with a denial. This statusindication may be provided to (or set by) emergency services server 138.If it is, it may be used to determine whether or not to send a requestto smartphone 104. If there is an acceptance, at 608, an acceptanceresponse may be sent using smartphone 104.

At 612, in response to the acceptance, smartphone 104 may receivedirectional routing to the emergency location. Emergency services server138 may generate routing information and send it to smartphone 104. Therouting may be, for example, in the form of a rendered roadmapindicating the emergency location and one or more routes. A route may beperiodically updated and may include the determined fastest route to theemergency location. Smartphone 104 may also receive other data, such asmultimedia files or text, from, for example, emergency services server138. This data may include, for example, emergency request datasubmitted as depicted and described in relation to FIG. 3.

At 616, smartphone 104 may provide information to emergency servicesserver 138. For example, a user may send files, messages, or otherinformation to emergency services server 138. For example, a firstresponder may wish to provide additional information regarding theemergency. This may be submitted as depicted and described in relationto FIG. 3. Communications between emergency services server 138 andsmartphone 104 may be logged by smartphone 104 or emergency servicesserver 138, or both.

FIG. 7 is a depiction of an exemplary dashboard illustrating aspects ofthe present disclosure. Dashboard 700 may be generated, for example, byemergency services server 138. Dashboard 700 may be a user interfacewith a graphical representation of aspects of the present disclosure.Dashboard 700 may include interactive and non-interactive elements.Dashboard 700 may be partially or entirely generated by emergency server138. Dashboard 700 may be stored and run on emergency server 138 or aseparate device, and the separate device may be in communication withemergency server 138. Dashboard 700 may be an XML dashboard or includeXML elements. Dashboard 700 may be or include a web site. Dashboard 700may incorporate dynamic elements updated based on, for example,real-time information and analysis. For example, dashboard 700 may beupdated based on emergency requests received by emergency server 138from smartphone 104, communications with user equipment 100, the statusof network elements, such as radio access technology 120, orcommunications with entity 140. For example, dashboard 700 may renderinformation based on communications received from or transmitted to userequipment 100 associated with a first responder. As another example,dashboard 700 may render information based on communications with adevice management server.

Dashboard 700 may include work area 704. Work area 704 may includestatic and dynamic elements. For example, work area 704 may includesearch pane 708. Search pane 708 may generate map 712 representing oneor more geographical regions, such as geographical regions 501 and 502as depicted in FIG. 3. Map 712 may also include candidate zone 716.Search pane 708 may be used to set or adjust candidate zone 716. Searchpane 708 may also display emergency response resources. For example, map712 may display resources as depicted in FIG. 5. Work area 704 may alsoinclude resource pane 720. Resource pane 720, as shown, includespersonnel resources, but may also include equipment (such as vehicles)or other resources. Resource pane 720 may display a list of resourcesarranged, for example, by an identifier, availability, suitableness(based on, for example, a score of the resource as determined for anemergency), or some combination of these and other factors. For example,entry 724 has no shading (corresponding to the shading used in FIG. 5)indicating the resource is not in use. Entry 724 includes an identifier(“Lee”) which may be a personal identifier. This personal identifier maybe, for example, a name associated with a user account provisioned for adevice, such as smartphone 104. The other available entries may be, forexample, randomly ordered, ordered by a suitability score,alphabetically, or other factors or a combination of factors. Entry 728as shown is rendered as being shaded slightly darker than the “availableentries” to indicate that user equipment 100 associated with “Adams” hasgiven an indication or it has otherwise been determined that theresource is involved in a low-priority engagement. Entry 732 as shown isrendered as another shade dark to indicate that user equipment 100associated with “Stevens” has given an indication or it has otherwisebeen determined that the resource is involved in a medium-priorityengagement. Entry 736 as shown is rendered as an even darker shade toindicate that user equipment associated with “Samuelson” is involved ina high-priority engagement. Entry 740 as shown has a line through it toindicate that a denial has been received from user equipment 100associated with the “Carson.” Other rendering and display techniques mayprovide indications of availability, suitability, order of requests, orother information. A user of dashboard 700 may change the order orclassification of one or more entries in resource pane 720. For example,a user may select entry 724 and delete it from resource pane 720 orchange its place in the order.

Work area 704 may include resource request list 742. Resource requestlist 742 may include entries corresponding to the resources evaluated asbeing required for the emergency. For example, two police units, afirefighting unit, and an ambulance unit may be required. Resources thathave already been requested and accepted may be listed, while unmetresources may have the requirement shown and the absence of a resourceindicated. For example, a police unit may be required. Entries inresource pane 720 may correspond to a candidate set of police resources,as described in relation to FIG. 4.

Work area 704 may also include feed pane 744. Feed pane 744 may displayand allow interaction and management of data received in connection withan emergency request. For example, an emergency request, as depicted anddescribed in relation to FIG. 3, may have been received by emergencyserver 138. The emergency request may have included a video, audio, andan image. Separately, there may be a video stream available from asecurity camera, such as camera 208. These files may be accessed throughdashboard 700. The files may be partially or wholly separated from anemergency request through dashboard 700 or otherwise. These files mayalso be sent using dashboard 700. These files may be sent, for example,in a request to a resource. For example, an interface element, such aselement 764 (depicted as a selection box), may be used to indicate thatthe data should be provided with or not provided with a request to aresource. For example, by selecting element 764, “BYSTANDER AUDIO” data752 would be sent as part of the request. For example, the “BYSTANDERVIDEO”, “BYSTANDER IMAGE”, and “SECURITY CAMERA STREAM” data may bepackaged by emergency services server 138 with a request to the userequipment 100 associated with the resource “Lee.”

Work area 704 may also include command pane 768. The command pane mayprovide direct control over functions of emergency services server 138.For example, emergency services server 138 may send requestsautomatically, without user interaction. Emergency services server 138may also send requests based on commands received from dashboard 700,such as commands sent through command pane 768. Work area 704 mayinclude softphone interface 772. Softphone interface 772 may include adial pad and may display a phone number of a caller or callee. Softphoneinterface 772 may allow for calls to be initiated using embedded,peripheral, or remote devices.

FIG. 8 illustrates an exemplary architecture of a mobile emergencyresponse network. Emergency responder network 804 may include, forexample, authentication server 808 and device management server 812.User equipment 100 may communicate with emergency responder network 804and may be provisioned by device management server 812 and may beauthenticated by authentication server 808. These may be the onlycommunications between user equipment 100 and emergency respondernetwork 804. PSAP network 816 may include PSAP terminal 820 and PSAPPrivate Branch Exchange (PBX) 824. PSAP network 816 may only be able toconnect with user equipment 100 through non-IP voice calls over a PublicSwitched Telephone Network (PSTN) through PSAP PBX 824. PSAP network 816may be unable to otherwise communicate or interact with user equipment100. PSAP network 816 may also have a limited number of lines. If allavailable lines are in use, calls may be rejected or redirected to avoicemail system. When, for example, PSAP PBX 824 receives a call, anindication may be sent by, for example, PSAP PBX 824 to emergencyservices server 138. The indication may be a message includinginformation such as a source location of the voice call, a phone number,whether the call was rejected, or other information. This may alsooccur, for example, when PSAP PBX 824 receives an IP voice call, MMSmessage, or other electronic communication it is unable to interpret orrespond to. When that occurs, the electronic communication may beredirected to emergency services server 138. PSAP network 816 may, forexample, provide information regarding an incompatible electroniccommunication to emergency services 816. For example, PSAP network 816may provide an indication to emergency services server 138 that anincompatible message has been received and, if possible, a time it wasreceived or a source phone number. Emergency services server 138 may bepart of one or more of emergency responder network 804 or PSAP network816. Emergency services server 138 may also be part oftelecommunications network 136. Emergency services server 138 may, forexample, connect to emergency response network 804 or PSAP network 816using a virtual private network (VPN) tunnel. This tunnel may be, forexample, a secure tunnel, such as a Secure Socket Tunneling Protocol(SSTP) tunnel. Emergency services server 138 may, for example, provide adashboard (such as depicted and described in relation in FIG. 7) to PSAPterminal 820. Emergency services server 138 may be in communication withuser equipment 100 as described herein, such as, for example, asillustrated and described in relation to FIGS. 4 and 6.

FIG. 9 illustrates an example wireless device 1010 (such as userequipment 100) that may be used in connection with an example of amobile emergency response network. References will also be made to otherfigures of the present disclosure as appropriate. For example, userequipment 100, such as smartphone 104 or tablet 108, may be wirelessdevices of the type described in regard to FIG. 9, and may have some,all, or none of the components and modules described in regard to FIG.9. It will be appreciated that the components and modules of wirelessdevice 1010 illustrated in FIG. 9 are illustrative, and that any numberand type of components and/or modules may be present in wireless device1010. In addition, the functions performed by any or all of thecomponents and modules illustrated in FIG. 9 may be performed by anynumber of physical components. Thus, it is possible that in someexamples the functionality of more than one component and/or moduleillustrated in FIG. 9 may be performed by any number or types ofhardware or hardware and software.

Processor 1021 may comprise any appropriate circuitry that performsoperations on behalf of wireless device 1010. Such circuitry may includehardware and other components that enable processor 1021 to perform anyof the functions and methods described herein. Such circuitry and othercomponents may also enable processor 1021 to communicate and/or interactwith other devices and components, for example any other component ofdevice of wireless device 1010, in such a manner as to enable processor118 and such other devices and/or components to perform any of thedisclosed functions and methods. In one example, processor 1021 executessoftware (i.e., computer readable instructions stored in a computerreadable medium) that may include functionality related to mobileemergency response, for example. User interface module 1022 may be anytype or combination of hardware and software that enables a user tooperate and interact with wireless device 1010, and, in one example, tointeract with a system enabling the user to place, request, and/orreceive calls, text communications of any type, voicemail, voicemailnotifications, voicemail content and/or data, and/or a system. Forexample, user interface module 1022 may include a display, physicaland/or “soft” keys, voice recognition software, a microphone, a touchscreen, a speaker, and the like. A display of user interface module 1022may display, for example, application graphical user interfaces (GUIs),text, images, video, telephony functions such as Caller ID data, setupfunctions, menus, music, metadata, messages, wallpaper, graphics,Internet content, device status, preference settings, map and locationdata, routes and other directions, points of interest (POI), and thelike. User interface module 1022 may provide information visually (via,for example, a display), audibly (via, for example, a speaker),mechanically (via, for example, a vibrating mechanism such as avibration motor), including haptically (or haptic feedback), or acombination thereof.

Wireless communication module 1023 may be any type of transceiverincluding any combination of hardware and software that enables wirelessdevice 1010 to communicate with wireless network equipment. Memory 1024enables wireless device 1010 to store information, such as APNs, MNCs,MCCs, text communications content and associated data, multimediacontent, software to efficiently process radio resource requests andservice requests, and radio resource request processing preferences andconfigurations. Memory 1024 may take any form, such as internal randomaccess memory (RAM), an SD card, a microSD card and the like. Powersupply 1025 may be a battery or other type of power input (e.g., acharging cable that is connected to an electrical outlet, etc.) that iscapable of powering wireless device 1010. SIM 1026 may be any type ofSubscriber Identity Module and may be configured on a removable ornon-removable SIM card that allows wireless device 1010 to store data onSIM 1026.

FIG. 10 is a block diagram of an example apparatus 1100 which may beemployed in any of the examples described herein, including as one ormore components of user equipment 100, emergency services server 138,and/or any related equipment and/or as one or more components of anythird party system or subsystem that may implement any portion of thesubject matter described herein. Apparatus 1100 may be a processor. Itis emphasized that the block diagram depicted in FIG. 10 is exemplaryand not intended to imply a specific implementation. Thus, the apparatus1100 may be implemented in a single processor or multiple processors.Multiple processors may be distributed or centrally located. Multipleprocessors can communicate wirelessly, via hard wire, or a combinationthereof. Apparatus 1100 may include circuitry and other components thatenable apparatus 1100 to perform any of the functions and methodsdescribed herein. Such circuitry and other components may also enableapparatus 1100 to communicate and/or interact with other devices andcomponents, for example any other component of any device disclosedherein or any other device, in such a manner as to enable apparatus 1100and such other devices and/or components to perform any of the disclosedfunctions and methods.

As depicted in FIG. 10, the apparatus 1100 may comprise a processingportion 1102, a memory portion 1104, and an input/output portion 1106.The processing portion 1102, memory portion 1104, and input/outputportion 1106 are coupled together (coupling not shown in FIG. 10) toallow communications between these portions. The input/output portion1106 is capable of providing and/or receiving components, commands,and/or instructions, utilized to, for example, request and receive APNs,MNCs, and/or MCCs, establish and terminate communications sessions,transmit and receive service requests and data access request data andresponses, transmit, receive, store and process text, data, and voicecommunications, execute software that efficiently processes radioresource requests, receive and store service requests and radio resourcerequests, radio resource request processing preferences andconfigurations, and/or perform any other function described herein.

The apparatus 1100 may be implemented as a client processor and/or aserver processor. In a basic configuration, the apparatus 1100 mayinclude at least one processing portion 1102 and memory portion 1104.The memory portion 1104 can store any information utilized inconjunction with establishing, transmitting, receiving, and/orprocessing text, data, and/or voice communications,communications-related data and/or content, voice calls, othertelephonic communications, etc. For example, the memory portion iscapable of storing APNs, MNCs, MCCs, service requests, radio resourcerequests, QoS and/or APN parameters, software for a mobile emergencyresponse network, text and data communications, calls, voicemail,multimedia content, visual voicemail applications, etc. Depending uponthe exact configuration and type of processor, the memory portion 1104can be volatile (such as RAM) 1108, non-volatile (such as ROM, flashmemory, etc.) 1110, or a combination thereof. The apparatus 1100 canhave additional features/functionality. For example, the apparatus 1100may include additional storage (removable storage 1112 and/ornon-removable storage 1114) including, but not limited to, magnetic oroptical disks, tape, flash, smart cards or a combination thereof.Computer storage media, such as memory and storage elements 1104, 1108,1110, 1112, and 1114, may include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer readable instructions, datastructures, program modules, or other data. Computer storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory, smart cards, or any other medium that can be used tostore the desired information and that can be accessed by the apparatus1100. Any such computer storage media may be part of the apparatus 1100.Any computer-readable storage medium described herein, including memory,is not to be construed as a signal, transient signal, or propagatingsignal. Memory, as well as any computer-readable storage mediumdescribed herein, is to be construed as an article of manufacture.

The apparatus 1100 may also contain the communications connection(s)1120 that allow the apparatus 1100 to communicate with other devices,for example through a radio access network (RAN). Communicationsconnection(s) 1120 is an example of communication media. Communicationmedia typically embody computer-readable instructions, data structures,program modules or other data in a modulated data signal such as acarrier wave or other transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection as might be used with a land line telephone, andwireless media such as acoustic, RF, infrared, cellular, and otherwireless media. The term computer-readable media as used herein includesboth storage media and communication media. The apparatus 1100 also canhave input device(s) 1116 such as keyboard, keypad, mouse, pen, voiceinput device, touch input device, etc. Output device(s) 1118 such as adisplay, speakers, printer, etc., also can be included.

A RAN as described herein may comprise any telephony radio network, orany other type of communications network, wireline or wireless, or anycombination thereof. The following description sets forth some exemplarytelephony radio networks, such as the global system for mobilecommunications (GSM), and non-limiting operating environments. Thebelow-described operating environments should be considerednon-exhaustive, however, and thus the below-described networkarchitectures merely show how mobile emergency response networks may beimplemented with stationary and non-stationary network structures andarchitectures. It can be appreciated, however, that mobile emergencyresponse networks as described herein may be incorporated with existingand/or future alternative architectures for communication networks aswell.

The GSM is one of the most widely utilized wireless access systems intoday's fast growing communication environment. The GSM providescircuit-switched data services to subscribers, such as mobile telephoneor computer users. The General Packet Radio Service (GPRS), which is anextension to GSM technology, introduces packet switching to GSMnetworks. The GPRS uses a packet-based wireless communication technologyto transfer high and low speed data and signaling in an efficientmanner. The GPRS attempts to optimize the use of network and radioresources, thus enabling the cost effective and efficient use of GSMnetwork resources for packet mode applications.

The exemplary GSM/GPRS environment and services described herein alsomay be extended to 3G services, such as Universal Mobile TelephoneSystem (UMTS), Frequency Division Duplexing (FDD) and Time DivisionDuplexing (TDD), High Speed Packet Data Access (HSPDA), cdma2000 1Evolution Data Optimized (EVDO), Code Division Multiple Access-2000(cdma2000 3), Time Division Synchronous Code Division Multiple Access(TD-SCDMA), Wideband Code Division Multiple Access (WCDMA), EnhancedData GSM Environment (EDGE), International MobileTelecommunications-2000 (IMT-2000), Digital Enhanced CordlessTelecommunications (DECT), 4G Services such as Long Term Evolution(LTE), etc., as well as to other network services that become availablein time. In this regard, systems, methods, and apparatuses for mobileemergency response networks may be applied independently of the methodof data transport and does not depend on any particular networkarchitecture or underlying protocols.

FIG. 11 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, that may beutilized to facilitate intelligent traffic routing, as described herein.In the example packet-based mobile cellular network environment shown inFIG. 11, there are a plurality of Base Station Subsystems (BSS) 1200(only one is shown), each of which comprises a Base Station Controller(BSC) 1202 serving a plurality of Base Transceiver Stations (BTS) suchas BTSs 1204, 1206, and 1208. BTSs 1204, 1206, 1208, etc. are the accesspoints where users of packet-based mobile devices become connected tothe wireless network. In example fashion, the packet traffic originatingfrom user devices is transported via an over-the-air interface to a BTS1208, and from the BTS 1208 to the BSC 1202. Base station subsystems,such as BSS 1200, are a part of internal frame relay network 1210 thatcan include Service GPRS Support Nodes (SGSN) such as SGSN 1212 and1214. Each SGSN is connected to an internal packet network 820 throughwhich a SGSN 1212, 1214, etc., can route data packets to and from aplurality of gateway GPRS support nodes (GGSN) 1222, 1224, 1226, etc. Asillustrated, SGSN 1214 and GGSNs 1222, 1224, and 1226 are part ofinternal packet network 1220. Gateway GPRS serving nodes 1222, 1224 and1226 mainly provide an interface to external Internet Protocol (IP)networks such as Public Land Mobile Network (PLMN) 1250, corporateintranets 1240, or Fixed-End System (FES) or the public Internet 1230.As illustrated, subscriber corporate network 1240 may be connected toGGSN 1224 via firewall 1232; and PLMN 1250 is connected to GGSN 1224 viaboarder gateway router 1234. The Remote Authentication Dial-In UserService (“RADIUS”) server 1242 may be used for caller authenticationwhen a user of a mobile cellular device calls corporate network 1240.

Generally, there may be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto, and umbrella cells. The coverage areaof each cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential environments, orsmall business environments. On the other hand, umbrella cells are usedto cover shadowed regions of smaller cells and fill in gaps in coveragebetween those cells.

FIG. 11 illustrates an architecture of a typical GPRS network that maybe utilized to facilitate intelligent traffic routing, as describedherein. The architecture depicted in FIG. 11 may be segmented into fourgroups: users 1350, radio access network 1360, core network 1370, andinterconnect network 1380. Users 1350 comprise a plurality of end users.Note, user equipment 100 is referred to as a mobile subscriber in thedescription of network shown in FIG. 11. In an aspect, the devicedepicted as mobile subscriber 1355 comprises a communications device(e.g., smartphone 104). Radio access network 1360 comprises a pluralityof base station subsystems such as BSSs 1362, which include BTSs 1364and BSCs 1366. Core network 1370 comprises a host of various networkelements. As illustrated in FIG. 11, core network 1370 may compriseMobile Switching Center (MSC) 1371, Service Control Point (SCP) 1372,gateway MSC 1373, SGSN 1376, Home Location Register (HLR) 1374,Authentication Center (AuC) 1375, Domain Name Server (DNS) 1377, andGGSN 1378. Interconnect network 1380 also comprises a host of variousnetworks and other network elements. As illustrated in FIG. 11,interconnect network 1380 comprises Public Switched Telephone Network(PSTN) 1382, Fixed-End System (FES) or Internet 984, firewall 1388, andCorporate Network 1389.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 1371, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (PSTN) 1382 through Gateway MSC (GMSC)1373, and/or data may be sent to SGSN 1376, which then sends the datatraffic to GGSN 1378 for further forwarding.

When MSC 1371 receives call traffic, for example, from BSC 1366, itsends a query to a database hosted by SCP 1372. The SCP 1372 processesthe request and issues a response to MSC 971 so that it may continuecall processing as appropriate.

The HLR 1374 is a centralized database for users to register to the GPRSnetwork. HLR 1374 stores static information about the subscribers suchas the International Mobile Subscriber Identity (IMSI), subscribedservices, and a key for authenticating the subscriber. HLR 1374 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 1374 is AuC 1375. AuC 1375 isa database that contains the algorithms for authenticating subscribersand includes the associated keys for encryption to safeguard the userinput for authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device (such as user equipment 100), used by anend user of the mobile cellular service. When a mobile subscriber turnson his or her mobile device, the mobile device goes through an attachprocess by which the mobile device attaches to an SGSN of the GPRSnetwork. In FIG. 11, when mobile subscriber 1355 initiates the attachprocess by turning on the network capabilities of the mobile device, anattach request is sent by mobile subscriber 1355 to SGSN 1376. The SGSN1376 queries another SGSN, to which mobile subscriber 712 was attachedbefore, for the identity of mobile subscriber 1355. Upon receiving theidentity of mobile subscriber 1355 from the other SGSN, SGSN 1376requests more information from mobile subscriber 1355. This informationis used to authenticate mobile subscriber 1355 to SGSN 1376 by HLR 1374.Once verified, SGSN 1376 sends a location update to HLR 1374 indicatingthe change of location to a new SGSN, in this case SGSN 1376. HLR 1374notifies the old SGSN, to which mobile subscriber 1355 was attachedbefore, to cancel the location process for mobile subscriber 1355. HLR1374 then notifies SGSN 1376 that the location update has beenperformed. At this time, SGSN 1376 sends an Attach Accept message tomobile subscriber 1355, which in turn sends an Attach Complete messageto SGSN 1376.

After attaching itself with the network, mobile subscriber 1355 thengoes through the authentication process. In the authentication process,SGSN 1376 sends the authentication information to HLR 1374, which sendsinformation back to SGSN 1376 based on the user profile that was part ofthe user's initial setup. The SGSN 1376 then sends a request forauthentication and ciphering to mobile subscriber 712. The mobilesubscriber 1355 uses an algorithm to send the user identification (ID)and password to SGSN 1376. The SGSN 1376 uses the same algorithm andcompares the result. If a match occurs, SGSN 1376 authenticates mobilesubscriber 1355.

Next, the mobile subscriber 1355 establishes a user session with thedestination network, corporate network 1389, by going through a PacketData Protocol (PDP) activation process. Briefly, in the process, mobilesubscriber 1355 requests access to the Access Point Name (APN), forexample, UPS.com, and SGSN 1376 receives the activation request frommobile subscriber 1355. SGSN 1376 then initiates a Domain Name Service(DNS) query to learn which GGSN node has access to the UPS.com APN. TheDNS query is sent to the DNS server within the core network 1370, suchas DNS 1377, which is provisioned to map to one or more GGSN nodes inthe core network 1370. Based on the APN, the mapped GGSN 1378 can accessthe requested corporate network 1389. The SGSN 1376 then sends to GGSN1378 a Create Packet Data Protocol (PDP) Context Request message thatcontains necessary information. The GGSN 1378 sends a Create PDP ContextResponse message to SGSN 1376, which then sends an Activate PDP ContextAccept message to mobile subscriber 1355.

Once activated, data packets of the call made by mobile subscriber 1355can then go through radio access network 1360, core network 1370, andinterconnect network 1380, in a particular fixed-end system or Internet1384 and firewall 1388, to reach corporate network 1389.

FIG. 14 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture that may be utilized to facilitateintelligent traffic routing, as described herein. As illustrated, thearchitecture of FIG. 14 includes a GSM core network 1400, a GPRS network1430 and an IP multimedia network 1438. The GSM core network 1401includes a Mobile Station (MS) 1402, at least one Base TransceiverStation (BTS) 1404 and a Base Station Controller (BSC) 1406. The MS 1402is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber Identity Module (SIM) or a Universal Integrated Circuit Card(UICC). The SIM or UICC includes an International Mobile SubscriberIdentity (IMSI), which is a unique identifier of a subscriber. The BTS1404 is physical equipment, such as a radio tower, that enables a radiointerface to communicate with the MS. Each BTS may serve more than oneMS. The BSC 1406 manages radio resources, including the BTS. The BSC maybe connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1403.

The GSM core network 1401 also includes a Mobile Switching Center (MSC)1008, a Gateway Mobile Switching Center (GMSC) 1410, a Home LocationRegister (HLR) 1412, Visitor Location Register (VLR) 1414, anAuthentication Center (AuC) 1418, and an Equipment Identity Register(EIR) 1416. The MSC 1408 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1410 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1420. Thus, the GMSC 1410 providesinterworking functionality with external networks.

The HLR 1412 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 1412 also contains the current location of each MS. The VLR 1414 isa database that contains selected administrative information from theHLR 1412. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1412 and the VLR 1414,together with the MSC 1408, provide the call routing and roamingcapabilities of GSM. The AuC 1416 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1418 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1409 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1402. A PushProxy Gateway (PPG) 1411 is used to “push” (i.e., send without asynchronous request) content to the MS 1002. The PPG 1411 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1402. A Short Message Peer to Peer (SMPP) protocol router 1413is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. The SMPP protocolis often used to allow third parties, e.g., content suppliers such asnews organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1402 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1404 and the BSC 1406.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 1430 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1432, a cell broadcast and a GatewayGPRS support node (GGSN) 1434. The SGSN 1432 is at the same hierarchicallevel as the MSC 1408 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1402. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 1433 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1434 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1436. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1436, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 1430 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vice versa.

The IP multimedia network 1438 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1440 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1440 are a call/session control function (CSCF),a media gateway control function (MGCF) 1446, a media gateway (MGW)1448, and a master subscriber database, called a home subscriber server(HSS) 1450. The HSS 1450 may be common to the GSM network 1401, the GPRSnetwork 1430 as well as the IP multimedia network 1438.

The IP multimedia system 1440 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1043, a proxy CSCF (P-CSCF) 1042, and a serving CSCF (S-CSCF) 1444. TheP-CSCF 1042 is the MS's first point of contact with the IMS 1440. TheP-CSCF 1442 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1442 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1443 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1443 may contact asubscriber location function (SLF) 1445 to determine which HSS 1450 touse for the particular subscriber, if multiple HSSs 1450 are present.The S-CSCF 1444 performs the session control services for the MS 1402.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1444 alsodecides whether an application server (AS) 1452 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1450 (or other sources, such as an application server 1452). TheAS 1452 also communicates to a location server 1456 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1402.

The HSS 1450 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1450, a subscriber location function providesinformation on the HSS 1450 that contains the profile of a givensubscriber.

The MGCF 1446 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1440 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1448 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1448 alsocommunicates with other IP multimedia networks 1454.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 15 illustrates a PLMN block diagram view of an exemplaryarchitecture in which mobile emergency response may be incorporated.Mobile Station (MS) 1501 is the physical equipment used by the PLMNsubscriber. In one illustrative example, communications device 40 mayserve as Mobile Station 1501. Mobile Station 1501 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

Mobile Station 1501 may communicate wirelessly with Base Station System(BSS) 1510. BSS 1510 contains a Base Station Controller (BSC) 1511 and aBase Transceiver Station (BTS) 1512. BSS 1510 may include a single BSC1511/BTS 1512 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1510 is responsible for communicating withMobile Station 1501 and may support one or more cells. BSS 1510 isresponsible for handling cellular traffic and signaling between MobileStation 1501 and Core Network 1540. Typically, BSS 1510 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1501 may communicate wirelessly with RadioNetwork System (RNS) 1520. RNS 1520 contains a Radio Network Controller(RNC) 1521 and one or more Node(s) B 1322. RNS 1320 may support one ormore cells. RNS 1520 may also include one or more RNC 1521/Node B 1522pairs or alternatively a single RNC 1521 may manage multiple Nodes B1522. RNS 1520 is responsible for communicating with Mobile Station 1501in its geographically defined area. RNC 1521 is responsible forcontrolling the Node(s) B 1522 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1521 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1501's access to the Core Network (CN) 1540.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1530 is aradio access network that provides wireless data communications forMobile Station 1501 and User Equipment 1502. E-UTRAN 1530 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1530 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1531 and E-UTRAN Node B (eNB) 1532. E-UTRAN 1530 may contain oneor more eNBs. User Equipment 1502 may be any user device capable ofconnecting to E-UTRAN 1530 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1530. The improvedperformance of the E-UTRAN 1530 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary mobile data and communication service that may beimplemented in the PLMN architecture described in FIG. 15 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1501 may communicate with any or all of BSS1510, RNS 1520, or E-UTRAN 1530. In an illustrative system, each of BSS1510, RNS 1520, and E-UTRAN 1530 may provide Mobile Station 1501 withaccess to Core Network 1540. The Core Network 1540 may include of aseries of devices that route data and communications between end users.Core Network 1540 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1541 is part ofCore Network 1540, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1560 and Gateway MSCServer 1561 in order to facilitate Core Network 1540 resource control inthe CS domain. Functions of CS-MGW 1541 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1540 mayreceive connections to Mobile Station 1501 through BSS 1510, RNS 1520 orboth.

Serving GPRS Support Node (SGSN) 1542 stores subscriber data regardingMobile Station 1501 in order to facilitate network functionality. SGSN1542 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1542 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1544 address for each GGSN where an active PDPexists. GGSN 1544 may implement a location register function to storesubscriber data it receives from SGSN 1542 such as subscription orlocation information.

Serving Gateway (S-GW) 1543 is an interface which provides connectivitybetween E-UTRAN 1530 and Core Network 1540. Functions of S-GW 1543include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1550, and mobility anchoring forinter-network mobility. PCRF 1550 uses information gathered from S-GW1543, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1545 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1563 is a database for user information,and stores subscription data regarding Mobile Station 1501 or UserEquipment 1502 for handling calls or data sessions. Networks may containone HSS 1563 or more if additional resources are required. Exemplarydata stored by HSS 1563 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1563 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1560 provides user location functionality. WhenMobile Station 1501 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1560, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1501 registration orprocedures for handover of Mobile Station 1501 to a different section ofthe Core Network 1540. GMSC Server 1561 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1562 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1501. In a typical example, user equipment may be classified aseither “white listed” or “black listed” depending on its status in thenetwork. In one example, if Mobile Station 1501 is stolen and put to useby an unauthorized user, it may be registered as “black listed” in EIR1562, preventing its use on the network. Mobility Management Entity(MME) 1564 is a control node which may track Mobile Station 1501 or UserEquipment 1502 if the devices are idle. Additional functionality mayinclude the ability of MME 1564 to contact an idle Mobile Station 1501or User Equipment 1502 if retransmission of a previous session isrequired.

While example embodiments of mobile emergency response networks havebeen described in connection with various computing devices/processors,the underlying concepts may be applied to any computing device,processor, or system capable of facilitating intelligent trafficrouting. The various techniques described herein may be implemented inconnection with hardware or software or, where appropriate, with acombination of both. Thus, the methods and apparatuses of mobileemergency response networks, or certain aspects or portions thereof, maytake the form of program code (i.e., instructions) embodied in concrete,tangible, storage media having a concrete, tangible, physical structure.Examples of tangible storage media include floppy diskettes, CD-ROMs,DVDs, hard drives, or any other tangible machine-readable storage medium(computer-readable storage medium). Thus, a computer-readable storagemedium is not a signal. A computer-readable storage medium is not atransient signal. Further, a computer-readable storage medium is not apropagating signal. A computer-readable storage medium as describedherein is an article of manufacture. When the program code is loadedinto and executed by a machine, such as a computer, the machine becomesan apparatus for intelligent traffic routing, on user equipment asdescribed herein. In the case of program code execution on programmablecomputers, the computing device will generally include a processor, astorage medium readable by the processor (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. The program(s) can be implemented inassembly or machine language, if desired. The language can be a compiledor interpreted language, and combined with hardware implementations.

The methods and apparatuses associated with mobile emergency responsenetworks as described herein also may be practiced via communicationsembodied in the form of program code that is transmitted over sometransmission medium, such as over electrical wiring or cabling, throughfiber optics, or via any other form of transmission, wherein, when theprogram code is received and loaded into and executed by a machine, suchas an EPROM, a gate array, a programmable logic device (PLD), a clientcomputer, or the like, the machine becomes an apparatus for implementingintelligent traffic routing as described herein. When implemented on ageneral-purpose processor, the program code combines with the processorto provide a unique apparatus that operates to invoke the functionalityof intelligent traffic routing as described herein.

While mobile emergency response networks have been described inconnection with the various embodiments of the various figures, it is tobe understood that other similar embodiments may be used ormodifications and additions may be made to the described embodiments ofmobile emergency response networks without deviating therefrom. Forexample, one skilled in the art will recognize that mobile emergencyresponse networks as described in the instant application may apply toany environment, whether wired or wireless, and may be applied to anynumber of such devices connected via a communications network andinteracting across the network. Therefore, mobile emergency responsenetworks as described herein should not be limited to any singleembodiment, but rather should be construed in breadth and scope inaccordance with the appended claims.

What is claimed:
 1. An emergency services server comprising: aprocessor; and a memory coupled to the processor, the memory comprisingexecutable instructions that when executed by the processor cause theprocessor to effectuate operations comprising: receiving a file defininga geographic area of emergency; receiving an emergency message over awireless communication channel from a remote mobile device, theemergency message comprising a multimedia data file, wherein themultimedia data file comprises metadata; separating the multimedia filefrom the emergency message; extracting a location value from themetadata; generating an emergency responder request comprising themultimedia data file; defining, based on the geographic area ofemergency and the location value, a candidate region; identifying acandidate mobile device within the candidate region, wherein thecandidate mobile device is not the remote mobile device; andtransmitting the emergency responder request over a second wirelesscommunication channel to the candidate mobile device.
 2. The emergencyservices server of claim 1, wherein the emergency responder request istransmitted to the candidate mobile device responsive to receipt of anindication that a Private Branch Exchange (PBX) associated with a PublicSafety Answering Point (PSAP) has received a voice call.
 3. Theemergency services server of claim 2, wherein the indication comprises asource telephone number associated with a voice call, and wherein theoperations further comprise: determining, based on the indication, asource location of the voice call, wherein the source location isdetermined based on location information received from a Home SubscriberServer (HSS).
 4. The emergency services server of claim 2, wherein theindication comprises a source telephone number associated with a voicecall, and wherein the operations further comprise: determining, based onthe indication, a source location of the voice call, wherein the sourcelocation is determined based on location information received from aMobile-Services Switching Center (MSC) Server.
 5. The emergency servicesserver of claim 1, wherein the operations further comprise: associatingthe candidate mobile device with a user account; and determining whetherto transmit the emergency responder request to the candidate mobiledevice based at least in part on an account status of the user account.6. The emergency services server of claim 5, wherein user account isreceived by the emergency services server from a mobile deviceprovisioning server.
 7. The emergency services server of claim 1,wherein the operations further comprise: receiving, from the candidatemobile device, responsive to the emergency responder request, arejection message.
 8. The emergency services server of claim 7, whereinthe rejection message is generated by an emergency services applicationon the candidate mobile device responsive to the emergency responderrequest based at least in part on an active status of the emergencyservices application.
 9. The emergency services server of claim 1,wherein the operations further comprise: receiving, from the candidatemobile device, responsive to the emergency responder request, anacceptance message generated by an emergency services applicationactivated on the candidate mobile device responsive to the emergencyresponder request.
 10. The emergency services server of claim 1, whereinthe remote mobile device comprises a Mobile Messaging Service (MMS)client and the emergency message comprises an MMS message.
 11. Theemergency services server of claim 10, wherein a second remote mobiledevice comprises an Extensible Messaging and Presence Protocol (XMPP)client and a second emergency message comprises an XMPP message.
 12. Amethod comprising: receiving a file defining a geographic area ofemergency; receiving an emergency message over a wireless communicationchannel from a remote mobile device, the emergency message comprising amultimedia data file, wherein the multimedia data file comprisesmetadata; separating the multimedia file from the emergency message;extracting a location value from the metadata; generating an emergencyresponder request comprising the multimedia data file; defining, basedon the geographic area of emergency and the location value, a candidateregion; identifying a candidate mobile device within the candidateregion, wherein the candidate mobile device is not the remote mobiledevice; and transmitting the emergency responder request over a secondwireless communication channel to the candidate mobile device.
 13. Themethod of claim 12, wherein the emergency responder request istransmitted to the candidate mobile device responsive to receipt of anindication that a Private Branch Exchange (PBX) associated with a PublicSafety Answering Point (PSAP) has received a voice call.
 14. The methodof claim 13, wherein the indication comprises a source telephone numberassociated with a voice call, and wherein the operations furthercomprise determining, based on the indication, a source location of thevoice call, wherein the source location is determined based on locationinformation received from a Home Subscriber Server (HSS).
 15. The methodof claim 14, wherein the indication comprises a source telephone numberassociated with a voice call, and wherein the method further comprises:determining, based on the indication, a source location of the voicecall, wherein the source location is determined based on locationinformation received from a Mobile-Services Switching Center (MSC)Server.
 16. The method of claim 12, further comprise: associating thecandidate mobile device with a user account; and determining whether totransmit the emergency responder request to the candidate mobile devicebased at least in part on an account status of the user account.
 17. Themethod of claim 12, wherein user account is received by the emergencyservices server from a mobile device provisioning server.
 18. The methodof claim 12, further comprise: receiving, from the candidate mobiledevice, responsive to the emergency responder request, a rejectionmessage.
 19. The method of claim 12, wherein the rejection message isgenerated by an emergency services application on the candidate mobiledevice responsive to the emergency responder request based at least inpart on an active status of the emergency services application.
 20. Themethod of claim 19, further comprise: receiving, from the candidatemobile device, responsive to the emergency responder request, anacceptance message generated by an emergency services applicationactivated on the candidate mobile device responsive to the emergencyresponder request.